EDI EDI Load option. For more information, see EDI Load form (on page 1). When you post an Inbound EDI message, you can post only containers. N4 does not support posting a container on a chassis through any EDI message. The inbound EDI processes are:
Load: N4 creates the EDI interchange using the following steps:
If you are using the EDI job schedule and FTP or SFTP, the Scheduler gets the EDI file from the client communication folder located on the FTP server and places the EDI file in the local EDI mailbox folder for processing. If you are using the EDI job schedule and email, you must place the inbound EDI file in the local EDI folder. N4 uses the EDI folder you specify in the EDI Mailbox form (on page 1).
You can also manually load an EDI file using the Administration EDI EDI Load option. For more information, see EDI Load form (on page 1).
N4 parses the UNA or the ISA segments of the incoming EDI file to identify the delimiters for the EDI message.
If N4 does not find a delimiter in the EDI file, N4 uses the delimiter specified for the associated EDI session (on page 1).
If the EDI session does not specify a delimiter, N4 uses the default delimiter for the EDI Message Standard (ANSI or UN/EDIFACT) of the EDI message type (on page 1).
If N4 does not find a delimiter for the EDI message type, N4 displays an error.
N4 divides the EDI file into segments using the segment delimiter, and then writes the segments to the Segments table for an EDI interchange. You can view the segments in an EDI interchange on the Segment tab (on page 1).
Classify: N4 determines the contents of the EDI interchange and segregates the segments into individual batches based on the message types included in the EDI interchange:
N4 searches the UNH or the ISA header segment to determine the EDI standard, such as UN/EDIFACT or ANSI, and to identify the EDI trading partner (on page 1).
N4 determines the EDI message type, version, and release number and then uses the appropriate EDI session.
N4 validates the value in the Version field against the UNH 0052 data element in the EDI file. Consequently, what appears in the 0052 UNH segment must match what is specified for the EDI message type for all associated EDI messages. For example, you enter D in the Version field, the EDI file must include "D" in the 0052 data segment after the message ID as follows: UNH+32454295-001+COPARN:D:95B:ITG13. If these version values do not match, N4 displays an error. In earlier versions of N4, the version number was driven off of the 0057 data element, but this is no longer the case.
Map: N4 creates the EDI transactions (on page 1) using the following steps:
N4 reads the segments from the Segments table, and then translates the segments into XML using the mapping file. For more information on mapping files, see EDI Message Map form (on page 1).
N4 creates the EDI transactions for all of the segments found, and then applies EDI filters (on page 1) to the transactions.
You can now define the transship port in the LOC+13 segment in the COPARN message.
Post: N4 creates an EDI batch for each EDI message type in an EDI interchange. If you selected the Autopost option for the EDI session, N4 posts the batches automatically. You can also manually post an EDI interchange using the EDI Batch Inspector (on page 1) Actions Post option.
N4 posts EDI messages in the order that the messages are received.
Also see How N4 determines to search the inbound vessel visit when you post the EDI COARRI activity message (on page 1).
For more information on inbound EDI processes, see STOWPLAN (on page 1), BOOKING (on page 1), or ACKNOWLEDGEMENT EDI processes (on page 1).
How N4 determines to search the inbound vessel visit when you post the EDI COARRI activity message?
When you post the EDI Container Loading Discharging Order (COARRI) activity inbound message with 'inOperatorVoyageNbr' value, then N4 searches the inbound vessel visit based on the line voyage number (Inbound), line operator, and other vessel/vessel visit values. When you post the same message with 'inVoyageNbr' value, then N4 searches the inbound vessel visit based on the voyage number and other vessel/vessel visit values.
When you post the COARRI inbound message with an invalid operator voyage number, N4 does not process the message and displays errors.